feat(work-items): integrate at least daily in decompose's window bar - #8382

Closes #8328

Summary

/work-items:decompose's window-bar row keeps the one-fresh-context-window bar and adds that a vertical slice can merge to the mainline at least daily. The cadence is practice guidance, the merge floor, not an estimate: the row states no hours unit, no time estimate and no day cap.

Fix

• plugins/work-items/skills/decompose/SKILL.md: the window-bar row adds the daily-integration clause, forbids a time estimate or day cap beside the existing token-budget ban, and points at DORA, trunk-based development and Fowler, Continuous Integration with an as-of date and recheck trigger.
• New eval case plugins/work-items/evals/decompose-slice-checks-daily-integration: an LLM judge on the window-bar verdict, a regex that the reply states daily integration, and a regex that it gives no hours estimate, with labeled samples for both regexes.
• The first paid run showed every with-arm reply wording the floor as "merge it the same day" or "within a day", which the judge passed and which meets the floor, while the regex demanded the literal "at least daily". The regex now also accepts those two forms (commit 78a0c17), with samples for each and a negated same-day fail.
• Changelog fragment .changes/work-items/feat-8328-decompose-daily-integration-6b1e4d9a.md.

Acceptance criteria

• grep -c "at least daily" on the decompose SKILL.md returns 1; grep -ciE "[0-9]+ hours" returns 0.
• Eval case (a case.yaml dir under the work-items plugin's evals/): a slice sized to the window bar is also checked for daily integration, with no hours estimate.
• The wording is confirmed against the Problem First effort's time-units rule (comment on #8328).
• After the commit, bash scripts/check-changed-skills.sh origin/main exits 0 (PASS, 0 errors, 4 pre-existing size and style warnings).
• A changelog fragment for the work-items plugin.

Verification

• scripts/check-affected.sh --tests: 7 passed, 2 skipped (shellcheck, ruff: no files of that kind changed).

• validate-cases.py plugins/work-items/evals: exit 0 (two WARN lines on the unrelated decompose-no-container-carries-brief case).

• Paid eval, claude plugin eval on Claude Code 2.1.303, model claude-opus-5-5, judge opus, 3 runs per arm, case decompose-slice-checks-daily-integration, plugin copied outside the repository:

  Plugin	With	Without	Delta	Validity
  This branch (grader fix applied)	1.00	0.33	+0.67	VALID
  main at 211a341 (the branch base) with the same case	0.33	0.33	0.00	VALID
  This branch, before the grader fix	0.67	0.33	+0.33	(superseded)

  The judge voted unanimously in all 6 runs of each pass. On main the with-arm applies the window bar but never states daily integration, so the judge and the daily regex fail; on the branch all three graders pass in every with-arm run. Noise report: n too small to call (one case; 3 or more needed for an interval), so this measures the case, not a suite-wide gain. List-price cost about 0.63 USD for the branch pass.

• Left out: judge calibration for applies-window-bar (it has no labeled samples, so it is reported uncalibrated); the validity gate's skill fired warning (the prompt loads the skill by its slash name, which the with-arm replies quote, and the case has no tool_used grader); main was measured at the branch base, not the main checkout, which was 81 commits behind.

Related

• Parent spec container: feat(planning): carry universal, overridable design defaults through planning output #8326.
• Agreed wording: Problem First effort's time-units rule, comment on #8328.

🤖 Generated with Claude Code